chore(deps-dev): bump nock from 14.0.17 to 15.0.3 by dependabot[bot] · Pull Request #2795 · slackapi/node-slack-sdk

dependabot · 2026-10-22T19:34:13Z

Bumps nock from 14.0.17 to 15.0.3.

Release notes

v15.0.3

15.0.3 (2026-10-19)

Bug Fixes

count bytes, not characters, for replyContentLength (#3007) (5bfb9ed), closes String#length #2294

v15.0.2

15.0.2 (2026-10-16)

Bug Fixes

don't decompress an empty request body (#3042) (76d2069), closes #3041

v15.0.1

15.0.1 (2026-10-06)

Bug Fixes

trigger release after merge v15 (#3021) (0d32f94)

v15.0.0

Released by accident, please use continue using v14 or v15@beta

... (truncated)

Commits

5bfb9ed fix: count bytes, not characters, for replyContentLength (#3007)
76d2069 fix: don't decompress an empty request body (#3042)
d91282e Update migration guide for version 15 changes
0d32f94 fix: trigger release after merge v15 (#3021)
bcd0200 feat!: v15.0.0 (#3017)
See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [nock](https://github.com/nock/nock) from 14.0.17 to 15.0.3. - [Release notes](https://github.com/nock/nock/releases) - [Changelog](https://github.com/nock/nock/blob/main/CHANGELOG.md) - [Commits](nock/nock@v14.0.17...v15.0.3) --- updated-dependencies: - dependency-name: nock dependency-version: 15.0.3 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>

changeset-bot · 2026-10-22T19:34:22Z

⚠️ No Changeset found

Latest commit: 637029e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

codecov · 2026-10-22T19:35:33Z

❌ 38 Tests Failed:

Tests completed	Failed	Passed	Skipped
301	38	263	0

View the top 3 failed test(s) by shortest run time

test::adds a single file data to uploads with content supplied

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::adds a single file data to uploads with file supplied

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::adds multiple files data to an upload

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::adds single and multiple files data to uploads

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::errors when appending to a completed stream

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::errors when appending to an unstarted stream

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::flushes both buffered markdown_text and chunks together

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::flushes chunks without buffered markdown_text

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::handles multiple files with a single channel_id, initial_comment and/or thread_ts

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::honours overriden token provided as an argument

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::honours overriden token provided as an argument

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::makes calls to files.completeUploadExternal for each fileUpload

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::makes calls to files.getUploadURLExternal for each fileUpload

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::rejects with an error when missing required file id

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::rejects with an error when missing required upload_url

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::retries a request which fails to get a response

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::retries a request whose response has a status code that is not 200 nor 429 (rate limited)

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::should allow concurrency to be set

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::should automatically retry the request after the specified timeout

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::should emit a rate_limited event on the client

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::should emit a rate_limited event on the client

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::should include retryAfter metadata if the response has retry info

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::should not send the token in the body if token is passed as a method argument

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::should not send the token in the body if token passed as client constructor

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::should pause the remaining requests in queue

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::should reject with a WebAPIRateLimitedError when a request fails due to rate-limiting

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::should throw an error if the response has an invalid retry-after header

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::should throw an error if the response has no retry info

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::should use a custom fetch function when provided via constructor

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::stops stream with chunks argument

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::streams a long message

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::streams a short message

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::the 'original' property is always attached to request errors

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::ts is undefined before flush and set after

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::uploads a single file

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::uploads content

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::uploads multiple files

Stack Traces | 0s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

test::should have a default conncurrency of 100

Stack Traces | 0.214s run time

Error [ERR_TEST_FAILURE]: Promise resolution is still pending but the event loop has already resolved
    at process.emit (node:events:519:28) {
  code: 'ERR_TEST_FAILURE',
  failureType: 'cancelledByParent',
  cause: 'Promise resolution is still pending but the event loop has already resolved'
}

To view more test analytics, go to the Test Analytics Dashboard
_{📋 Got 3 mins? Take this short survey to help us improve Test Analytics.}

zimeg · 2026-10-22T20:04:16Z

Diagnosis from the heartbeat monitor: CI fails at npm ci before any tests run, with Missing: rettime@0.11.12 from lock file and Missing: @types/debug@4.1.13 from lock file. nock 15 adds new transitive dependencies, and the lockfile Dependabot generated does not include them, so this needs a regenerated lockfile (npm install at the workspace root) rather than a re-run. The same failure shows on #2792, #2793 and #2795, which supersede #2779, #2780 and #2782.

dependabot · 2026-10-29T19:34:16Z

Superseded by #2802.

dependabot Bot requested a review from a team as a code owner October 22, 2026 19:34

dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Oct 22, 2026

dependabot Bot mentioned this pull request Oct 22, 2026

chore(deps-dev): bump nock from 14.0.17 to 15.0.1 #2782

Closed

zimeg marked this pull request as draft October 27, 2026 16:58

dependabot Bot closed this Oct 29, 2026

dependabot Bot deleted the dependabot/npm_and_yarn/nock-15.0.3 branch October 29, 2026 19:34

This was referenced Oct 29, 2026

chore(deps-dev): bump nock from 14.0.17 to 15.0.5 #2802

Closed

chore(deps-dev): bump nock to 15.0.5 and update web-api tests #2805

Closed

ci(dependabot): hold nock at 14.x while Node.js 20 is supported #2806

Merged

Navigation Menu

Repository navigation

chore(deps-dev): bump nock from 14.0.17 to 15.0.3 - #2795

chore(deps-dev): bump nock from 14.0.17 to 15.0.3#2795
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/nock-15.0.3

dependabot Bot commented on behalf of github Oct 22, 2026

Uh oh!

changeset-bot Bot commented Oct 22, 2026

Uh oh!

codecov Bot commented Oct 22, 2026 •

edited

Loading

Uh oh!

zimeg commented Oct 22, 2026

Uh oh!

dependabot Bot commented on behalf of github Oct 29, 2026

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

dependabot Bot commented on behalf of github Oct 22, 2026

v15.0.3

15.0.3 (2026-10-19)

Bug Fixes

v15.0.2

15.0.2 (2026-10-16)

Bug Fixes

v15.0.1

15.0.1 (2026-10-06)

Bug Fixes

v15.0.0

Uh oh!

changeset-bot Bot commented Oct 22, 2026

⚠️ No Changeset found

Uh oh!

codecov Bot commented Oct 22, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

❌ 38 Tests Failed:

Uh oh!

zimeg commented Oct 22, 2026

Uh oh!

dependabot Bot commented on behalf of github Oct 29, 2026

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

codecov Bot commented Oct 22, 2026 •

edited

Loading